Service Gateway Decomposition in a Network Environment Including IMS

ABSTRACT

In one embodiment, a scheme is described with respect to a service network system adapted to interoperate in an Internet Protocol (IP) Multimedia Subsystem (IMS) environment wherein signaling and message media planes are decoupled. The service network system comprises a service gateway controller (SGC) that is decomposed from a plurality of a plurality of service gateways (SGWs) operable to effectuate a message transport interface with respect to a remote services server.

REFERENCE TO RELATED APPLICATION(S)

This application discloses subject matter that is related to the subjectmatter of the following U.S. patent application(s): (i) “ARCHITECTUREFOR SERVICE DELIVERY IN A NETWORK ENVIRONMENT INCLUDING IMS” (AttorneyDocket No. 1400-1066US; Client Reference No. 30765-US-PAT), applicationSer. No.: ______, filed even date herewith, in the name(s) of GiyeongSon, Allan D. Lewis and Bruno Preiss; (ii) “SIGNALING ARCHITECTURE FORDECOMPOSED SERVICE NETWORK ELEMENTS OPERABLE WITH IMS” (Attorney DocketNo. 1400-1066US2; Client Reference No. 32321-US-PAT), application Ser.No.: ______, filed even date herewith, in the name(s) of Giyeong Son,Allan D. Lewis and Bruno Preiss; (iii) “SCALABLE AND SECURE MESSAGINGSYSTEM FOR A WIRELESS NETWORK,” now published as U.S. Patent ApplicationPublication No. 2002/0132609, in the names of: Allan D. Lewis, TabithaK. Ferguson, James A. Godfrey, Carl L. Cherry and Bill Yuan; and (iv)“SYSTEM AND METHOD FOR PUSHING INFORMATION FROM A HOST SYSTEM TO AMOBILE DATA COMMUNICATION DEVICE,” now published as U.S. PatentApplication Publication No. 2004/0073619, in the names of: Barry J.Gilhuly, Anh Ngoc Van, Steven M. Rahn, Gary P. Mousseau and MihalLazaridis. Each of the foregoing patent applications is incorporated byreference herein.

FIELD OF THE DISCLOSURE

The present patent disclosure generally relates to communicationsnetworks. More particularly, and not by way of any limitation, thepresent patent disclosure is directed to an architecture for servicedelivery in a network environment including an IP Multimedia Subsystem(IMS) network.

BACKGROUND

Delivery of email messages to mobile handheld devices is well known.However, current techniques for achieving such delivery are generallynot concerned with the latest 3^(rd) Generation Partnership Project(3GPP) standards that specify a new, all IP-based network architecturereferred to as the IP Multimedia Subsystem (IMS).

Although IMS provides a well-defined architecture with respect tosession control and the underlying network infrastructure, it is silentregarding the service architecture inasmuch as service providers areresponsible for architecting their services over the IMS network. One ofthe issues is ensuring reliability and scalability of the servicearchitecture with respect to the services to be delivered over the IMSnetwork.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the embodiments of the present patentdisclosure may be had by reference to the following Detailed Descriptionwhen taken in conjunction with the accompanying drawings wherein:

FIG. 1 depicts a network communications environment including anenterprise network and IP Multimedia Subsystem (IMS) infrastructurewherein one or more embodiments of the present patent disclosure may bepracticed;

FIG. 2 depicts a flowchart associated with one or more exemplaryembodiments of the present patent disclosure for facilitating deliveryof data items over IMS;

FIG. 3A depicts another view of a network communications environmentwhere an IMS network and access networks are exemplified;

FIG. 3B depicts an architectural view of an IMS network operable forpurposes of the present patent disclosure;

FIG. 4 depicts a network architectural embodiment for facilitatingdelivery of data items to a mobile communications device;

FIG. 5 depicts a flowchart associated with one or more exemplaryembodiments of the present patent disclosure for effectuating deliveryof data items over IMS;

FIG. 6 depicts a flowchart associated with one or more exemplaryembodiments of the present patent disclosure for effectuating deliveryof a data item from an IMS-aware mobile communications device;

FIG. 7 depicts a flowchart relating to a service gateway decompositionscheme according to one embodiment;

FIG. 8 depicts a network architectural embodiment for facilitatingdelivery of data items over IMS wherein service gateway functionality isdecomposed in accordance with the teachings of the present patentdisclosure;

FIG. 9 depicts a network communications environment exemplifying servicegateway decomposition according to one embodiment; and

FIG. 10 depicts a block diagram of an embodiment of a communicationsdevice operable for purposes of the present patent disclosure.

DETAILED DESCRIPTION OF THE DRAWINGS

The present patent disclosure is broadly directed to a networkarchitecture and associated systems and methods for facilitatingdelivery of redirected data items over a communications network to amobile communications device, wherein the communications networkincludes an IMS network. In one embodiment, disclosed herein is aservice network system adapted to interoperate in an IMS environment.The claimed embodiment comprises one or more of the following: a servicegateway controller (SGC) operable to effectuate a signaling interfacewith respect to at least one remote services server; and a plurality ofservice gateways (SGWs) operably coupled to the SGC, the plurality ofSGWs for effectuating a message transport interface with respect to theat least one remote services server, wherein each of the plurality ofSGWs is configurable to be connected to the remote services server in adynamic routing arrangement.

In another embodiment, disclosed herein is a method of communicationcomprising one or more of the following features: contacting a networknode such as SGC disposed in an IMS network by a service client (SC)executing on a user equipment (UE) device, wherein the SGC is operablycoupled to a plurality of SGWs; discovering a particular SGW assigned tothe SC on the UE device; and receiving from the particular SGW one ormore data items redirected to the UE device by a remote services serverassociated therewith.

In a still further embodiment, disclosed herein is a wireless UE device,comprising one or more of the following features: means for contacting anetwork node such as SGC disposed in an IMS network by a service client(SC) executing on the wireless UE device, wherein the SGC is operablycoupled to a plurality of SGWs; means for discovering a particular SGWassigned to the SC on the wireless UE device; and means for receivingfrom the particular SGW one or more data items redirected to thewireless UE device by a remote services server associated therewith.

A system and method of the present patent disclosure will now bedescribed with reference to various examples of how the embodiments canbest be made and used. Like reference numerals are used throughout thedescription and several views of the drawings to indicate like orcorresponding parts, wherein the various elements are not necessarilydrawn to scale. Referring to the drawings, and more particularly to FIG.1, depicted therein is an exemplary network communications environment100 including an enterprise network 102 and an IMS network 120 whereinone or more embodiments of the present patent disclosure may bepracticed for purposes of facilitating delivery of data items to andfrom a mobile communications device 116. The enterprise network 102,which may be a packet-switched network, can include one or moregeographic sites and be organized as a local area network (LAN), widearea network (WAN) or metropolitan area network (MAN), et cetera, forserving a plurality of corporate users. A number of application servers104-1 to 104-N disposed as part of the enterprise network 102 areoperable to provide or effectuate a host of internal and externalservices such as email, video mail, Internet access, corporate dataaccess, messaging, calendaring and scheduling, information management,and the like. For instance, reference numeral 104-1 refers to acorporate email messaging system/server. A diverse array of personalinformation appliances such as desktop computers (e.g., computers 110-1through 110-N), laptop computers, palmtop computers, et cetera, althoughnot specifically shown in FIG. 1, may be operably networked to one ormore of the application servers 104-i, i=1, 2, . . . , N, with respectto the services supported in the enterprise network 102.

Additionally, a remote services server (RSS) 106 may be interfaced withthe enterprise network 102 for enabling a corporate user to access oreffectuate any of the services from a remote location using the mobilecommunications device (MCD) 116. To facilitate redirection orreplication of data items from an enterprise site (e.g., from a desktopcomputer, a user mailbox, or some other location) to MCD 116 for aparticular user, specialized software 112 may be provided that may beexecuted on the email server 104-1, on RSS 106, on a desktop computer,or as a separate application server in the enterprise network 102.Regardless of how such software is provisioned within the enterprisenetwork 102, a client software component 114 is operable to be executedon MCD 116 to which user-selectable data items may be redirected.

RSS 106 may be coupled via a public packet-switched network 108 (e.g.,the Internet) to the IMS core network 120 that provides a deliverymechanism with respect to the data items that are processed to beredirected to MCD 116. In one embodiment, MCD 116 may be operablyconnected to the IMS network 120 via a suitable access networkinfrastructure 118. As will be described in detail below, the IMSnetwork 120 includes suitable service gateway functionality as an IMSservice node (i.e., application server) operable to transmit theprocessed data items or portions thereof to MCD 116.

In general, a variety of data items may be processed to be redirectedover the IMS network. By way of example, the data items may compriseemail messages, calendar events, meeting notifications, address or otherpersonal data assistant (PDA) entries, journal entries, personalreminders, Instant Messages (IM), multimedia notifications/messages(e.g., audio and/or video clips), or other items from an externalnetwork (e.g., stock quotations, news stories, podcasts, webcasts,content downloads, etc. that are pushed or otherwise provided to users).In one embodiment, the data items to be redirected may be detected byway of a polling mechanism wherein specialized software such as software112 may be configured to poll for certain data items (i.e., “pull”model) on behalf of a user authorized for receiving redirected dataitems at a wireless user equipment (UE) device such as MCD 116. In analternative embodiment, a “push” model may be employed wherein the dataitems to be redirected may be detected based on receiving automaticallygenerated notifications. Where the data items are stored in databases,changes to such databases (e.g., due to arrival of a new email, updatingof an address book, etc.) may be automatically provided to software 112(i.e., without it having to poll for the changes) via suitable adviserequests such as those provided by Messaging Application ProgrammingInterface (MAPI), for example. Additionally, regardless of whether apull model or a push model is employed for detecting the data items, anevent-driven scheme may also be provided such that redirection of a dataitem may be rendered dependent upon setting certain flags associatedwith user-selectable events (i.e., trigger events). That is, in otherwords, the redirection software 112 may be “turned on” or “turned off”based on whether a trigger event has occurred and, upon the occurrenceof the event (which may generate a signal that operates to set a triggerflag), new data items may be continuously redirected (i.e., withoutfurther global gating conditions). These user-defined trigger events mayinclude external events, internal events and networked events, or acombination thereof. Examples of external events include: receiving amessage from the user's MCD to begin redirection; receiving a similarmessage from some external computer; sensing that the user is no longerin the vicinity of the user's computer system; or any other event thatis external to the user's computer system. Internal events could be acalendar alarm, screen saver activation, keyboard timeout, programmabletimer, or any other user-defined event that is internal to the computersystem executing the redirection software 112. Networked events areuser-defined messages that are transmitted from another computer coupledto the system executing the redirection software 112 via a network(e.g., a LAN) to initiate redirection. These are just some of theexamples of the types of user-defined events that can trigger theredirector software 112 to initiate redirection of data items to theuser's MCD. As a further implementation, a variety of filtering schemesmay also be used for further modulating the redirection behaviorregardless of whether the redirection software is disposed within theenterprise or at a standalone desktop computer or operable inassociation with an Internet email system. Accordingly, thefunctionality of the redirection software 112 may comprise one or moreof the following: (1) configure and set up one or more user-definedtrigger events (which may be user-specific, time-window-specific, etc.)that will start redirection; (2) configure the types of user data itemsfor redirection and optionally configure a preferred list of messagesenders whose messages are to be redirected; (3) configure the type andcapabilities of the user's handheld equipment (e.g., MCD 116); (4)receive messages and signals from data item repackaging systems and theevent generating systems; and (5) command and control the redirection ofthe user-selected data items to the user's MCD the repackaging systems.Those skilled in the art will recognize that other functions andprocesses not specifically enumerated (e.g., processing of attachments,encryption, encoding/transcoding, compression, etc.) may also beintegrated into or otherwise associated with the functionality ofsoftware 112.

FIG. 2 depicts a flowchart associated with an exemplary embodiment 200of the present patent disclosure for facilitating delivery of data itemsover IMS based on a push model. As illustrated, redirector software 112,whose execution may be performed on different computers in a distributedcomputing environment, may be started and initially configured (blocks202 and 204) to set up the redirection process for one or more users. Asalluded to previously, the initial configuration of redirection software112 may include: (1) defining the trigger events or trigger points fortriggering redirection; (2) identifying one or more data item types forredirection; (3) selecting a repackaging sub-system, either standardemail or a special-purpose technique; (4) selecting the type of mobilecommunications device, indicating whether and what type of attachmentsthe device is capable of receiving and processing, and inputting anaddress of the mobile communications device; and (5) configuring one ormore lists, e.g., a preferred list of user-selectable senders whosemessages are to be redirected. If the redirection software 112 isexecutable on a network server, additional configuration steps may benecessary to enable redirection for a particular desktop system (e.g.,desktop computer 110-1 associated with a particular user shown in FIG.1), including: (1) setting up a profile for the desktop systemindicating its address, events that will trigger redirection, and thedata items that are to be redirected upon detecting an event; (2)maintaining a storage area at the server for the data items; and (3)storing the type of mobile communications device to which the desktopcomputer's data items are to be redirected, whether and what type ofattachments the device is capable of receiving and processing, as wellas an address of the mobile device. Once the redirector software isconfigured and the trigger points (or trigger events) are enabled(blocks 202 and 204), the redirector software is rendered into what maybe referred to as “redirection mode,” whereupon the software is operableto wait for data items and signals 206 such that redirection maycommence if a new data item is available (block 208). A data item couldbe an email message or some other user data item that may have beenselected for redirection, and a signal could be a trigger signalgenerated upon occurrence of a trigger event, or could be some othertype of signal that has not been configured as an event trigger. When amessage or signal is detected, the software is operable to determine(block 212) whether it is one of the trigger events that have beenconfigured to signal redirection. If so, then at block 210 a triggerflag is set, indicating that subsequently detected data items that havebeen selected for redirection should be processed and packaged intoprocessed information suitable for transmission to the user's MCD viaIMS. If the signal 206 is not indicative of a trigger event, thesoftware is operable to determine whether the data item is a systemalarm (block 214), an email message (block 216), or some other type ofinformation that has been selected for redirection (block 218). If thedata item or signal is none of these three items, then control returnsto block 208, where the redirector software continues to be in theredirection mode (i.e., waiting for additional messages, data items orsignals 206 to act upon). If, however the message is one of these threetypes of information, then upon determining that the trigger flag hasbeen set (block 220), the data item is indicated to be redirected to theMCD. If the trigger flag is set, the redirector software 112 causes arepackaging system (a standard email system or a TCP/IP-based system) toprocess and package the item for IMS delivery (block 222). At block 224,the processed/packaged data item is redirected to the user's MCD via IMSby directing the processed information to a suitable service gateway aswill be described in detail hereinbelow. Control then returns to block208 where the redirection software 112 continues to be in theredirection mode. Although not shown explicitly in FIG. 2, furtherdeterminations may be made after block 220 in order to verify whetherany number of user-specific, sender-specific, data item-specific,time-window-specific filtering schemes are satisfied. Additional detailsregarding the redirection software functionality and further variationstherein may be found in U.S. Pat. No. 6,219,694 (issued: Apr. 17, 2001)entitled “SYSTEM AND METHOD FOR PUSHING INFORMATION FROM A HOST SYSTEMTO A MOBILE DATA COMMUNICATION DEVICE HAVING A SHARED ELECTRONICADDRESS” in the names of Mihal Lazaridis and Gary P. Mousseau, which isassigned to the assignee of the present patent application andincorporated by reference herein.

Referring now to FIG. 3A, depicted therein is another view of a networkcommunications environment 300A where an IMS network and an accessnetwork space are exemplified for purposes of facilitating servicedelivery in accordance with the teachings of the present patentdisclosure. As illustrated, the network communications environment 300Aincludes an access space 304 comprised of a number of accesstechnologies available to a plurality of UE devices 302-1 through 302-N.For purposes of the present disclosure, a UE device may be any tetheredor untethered communications device, and may include any mobile personalcomputer (e.g., laptops, palmtops, or handheld computing devices)equipped with a suitable wireless modem or a mobile communicationsdevice (e.g., cellular phones or data-enabled handheld devices capableof receiving and sending messages, web browsing, et cetera), or anyenhanced PDA device or integrated information appliance capable ofemail, video mail, Internet access, corporate data access, messaging,calendaring and scheduling, information management, and the like.Preferably, the UE device is capable of operating in multiple modes inthat it can engage in both circuit-switched (CS) as well aspacket-switched (PS) communications, and can transition from one mode ofcommunications to another mode of communications without loss ofcontinuity and consume one or more IMS-based services. It will thereforebe realized that any UE device 302-1 through 302-N may be deemed to beillustrative of MCD 116 shown in FIG. 1.

The access space 304 may be comprised of both CS and PS networks, whichmay involve wireless technologies, wireline technologies, broadbandaccess technologies, etc. For example, reference numeral 306 refers towireless technologies such as Global System for Mobile Communications(GSM) networks and Code Division Multiple Access (CDMA) networks,although it is envisaged that the teachings hereof may be extended toany 3^(rd) Generation Partnership Project (3GPP)-compliant cellularnetwork (e.g., 3GPP or 3GPP2) as well. Reference numeral 308 refers tobroadband access networks including wireless local area networks orWLANs, Wi-MAX networks as well as fixed networks such as DSL, cablebroadband, etc. Thus, for purposes of the present disclosure, the accesstechnologies may comprise radio access technologies selected from IEEE802.11a technology, IEEE 802.11b technology, IEEE 802.11g technology,IEEE 802.11n technology, GSM/EDGE Radio Access Network (GERAN)technology (both CS and PS domains), and Universal MobileTelecommunications System (UMTS) technology, and Evolution-DataOptimized (EVDO) technology, and so on. Additionally, also exemplifiedas part of the access space 304 is conventional wireline PSTNinfrastructure 310 illustrated in FIG. 3A.

The access space 304, including any CS-based networks via suitablegateways, is coupled to the IMS core network 120. As is well known, theIMS core is operable according to the standards defined by the 3GPP andis designed to allow service providers manage a variety of services thatcan be delivered via IP over any network type, wherein IP is used totransport both bearer traffic and Session Initiation Protocol(SIP)-based signaling traffic. Broadly, IMS is a framework for managingthe applications (i.e., services) and networks (i.e., access) that iscapable of providing multimedia services. IMS defines an “applicationserver” as a network element that delivers services subscribers use,e.g., voice call continuity (VCC), Push-To-Talk (PTT), etc. IMS managesapplications by defining standardized interfaces and common controlcomponents that each application server (AS) is required to have, e.g.,subscriber profiles, IMS mobility, network access, authentication,service authorization, charging and billing, inter-operator functions,and interoperation with the legacy phone network.

It should be understood that whereas IMS is defined by the 3GPPstandards body which mainly addresses GSM networks, another group,3GPP2, is involved in defining a closely analogous architecture referredto as Multimedia Domain (MMD). MMD is essentially an IMS for CDMAnetworks, and since MMD and IMS are roughly equivalent, the term “IMS”may be used in this present patent disclosure to refer collectively toboth IMS and MMD where applicable. In addition, fixed network standardsfor NGN (Next Generation Networks) that are based on and/or reuse IMSare also being developed by bodies such as ETSI TISPAN, Cablelabs andthe ITU-T. NGN and IMS are roughly equivalent, and accordingly the term“IMS” may also be used in this present patent disclosure to refercollectively to both IMS and NGN where applicable.

Continuing to refer to FIG. 3A, reference numerals 314-1 to 314-N referto a plurality of AS nodes (also referred to as service gateways)operable to support various services, e.g., VCC, PTT, etc., alluded tohereinabove. Particularly, AS node 314-N embodies service gatewayfunctionality that is operable to effectuate remote services delivery(e.g., delivery of redirected data items such as email messages, forinstance) using the IMS infrastructure. Accordingly, AS node 314-N maybe operably coupled to RSS 106 in an exemplary embodiment, which in turnmay be disposed in an enterprise network as illustrated in FIG. 1.

FIG. 3B depicts an architectural view 300B of an IMS environment such asthe IMS core 120 operable for purposes of the present patent disclosure.As set forth above, the IMS core 120 is essentially a collection ofdifferent functions, linked by standardized interfaces, thereby formingone IMS administrative network. In general, a function is notnecessarily a “node” (i.e., a hardware box). A service provider mayimplement one or more functions in a single node, or segregate a singlefunction into more than one node. Further, each node may be presentmultiple times in a single network in order to achieve load balancing orother organizational objectives. Architecturally, the IMS environmentinvolves a transport layer 350A, an IMS core layer 350B and aservice/application layer 350C. The transport layer 350A comprisesvarious access technologies as alluded to previously, e.g.,circuit-switched network (CSN) technologies 352, WLAN technologies 354,DSLAM technologies 365, RAN technologies 358 and packet data network(PDN) technologies 360 based on IP version 4 or version 6. A number ofSIP servers or proxies, collectively referred to as Call Session ControlFunction (CSCF) 362, are operable as part of the IMS core layer 350B forprocessing SIP signaling packets in the IMS. A Proxy-CSCF (P-CSCF) 366is a SIP proxy that is usually the first contact point for an IMS-baseddevice. P-CSCF 366 may be located either in a visited network (in fullIMS networks) or in the subscriber's home network (when the visitednetwork is not IMS-compliant). The IMS-aware MCD may discover its P-CSCFwith either Dynamic Host Configuration Protocol (DHCP), or it may beassigned in a PDP context (e.g., in GPRS). A Serving-CSCF (S-CSCF) 364is operable as a central node of the IMS signaling plane, and is usuallylocated in the subscriber's home network. The functionality of S-CSCF364 includes interfacing with a Home Subscriber Server (HSS) 374 in theservice/application layer 350C to download and upload user profiles,policies, routing information relating to redirected data items, etc. AnInterrogating-CSCF (I-CSCF) 368 is another SIP functionality at the edgeof an administrative domain, which may be used for querying HSS 374 toretrieve the MCD location. In general, accordingly, the HSS database maycontain user profiles (i.e., subscription-related information),including various user and device identifies such as InternationalMobile Subscriber Identity (IMSI), Temporary Mobile Subscriber Identity(TMSI), International Mobile Equipment Identity (IMEI), MobileSubscriber ISDN Number (MSISDN), Universally Unique Identifier (UUID),as well as additional IMS-specific identities such as IP MultimediaPrivate Identity (IMPI) and IP Multimedia Public Identity (IMPU) thatare implemented as Tel-Uniform Resource Identifiers (URIs) or SIP-URIs.Whereas the IMPI is unique to a particular user or device in a 3GPP, itis possible to have multiple Public Identities (i.e., IMPUs) per IMPI.

Furthermore, the IMS layer 350B may also include other functions thatfacilitate call routing relative to a CSN such as a PLMN. For instance,a Breakout Gateway Control Function (BGCF) 370 includes routingfunctionality based on E.164 phone numbers when communicating to a phonein the PLMN. A Media Gateway Controller Function (MGCF) 372 includesfunctionality for effectuating call control protocol conversion betweenSIP and ISDN User Part (ISUP).

In addition to HSS 374, the service/application layer 350C includes oneor more AS nodes, e.g., AS 376, with appropriate interfacing with theentities in the IMS layer 350B for effectuating services orapplications. As pointed out previously, an AS node (i.e., servicegateway) may be provided for effectuating delivery of redirected dataitems using the IMS infrastructure. FIG. 4 depicts a networkarchitectural embodiment 400 that illustrates various entities, theirlogical elements and service flows for a formal model of providing emailservice delivery over IMS. A service gateway (SGW) 402 including aprotocol translation/conversion functionality 403 is coupled to one ormore email service server (ESS) entities 404 disposed in an externalnetwork 405 via an interface 412 that uses either standard orproprietary protocols. In turn, ESS entities 404, which may include theredirection software functionality described in the foregoing sections,are coupled to one or more mail messaging systems, e.g., messagingsystem 406 that may include a plurality of email servers 408-1 through408-N. Each email server is operable to serve a number of user mailboxesMB 410. To facilitate scalability and reliability, the messaging system406 may be architected as disclosed in the co-pending commonly assignedU.S. patent application Ser. No. 10/098,083 (filed: Mar. 14, 2002),entitled “SCALABLE AND SECURE MESSAGING SYSTEM FOR A WIRELESS NETWORK,”now published as U.S. Patent Application Publication No. 2002/0132609,in the names of: Allan D. Lewis, Tabitha K. Ferguson, James A. Godfrey,Carl L. Cherry and Bill Yuan, incorporated by reference herein.

By way of example, the interface 412 may employ a proprietary protocolsuch as Email Transport Protocol (ETP) for transmitting processedinformation between SGW 402 and ESS 404. Alternatively, the interface412 may employ standards-based protocols such as Simple Mail TransferProtocol (SMTP) or an Extended Markup Language (XML)-based protocol.Reference numeral 414 refers to exemplary signaling path via IMS 120between SGW 302 and Service Client (SC) software 415 executing on MCD116, effectuated using SIP. Reference numeral 416 refers to the messageflow path between MCD 116 and SGW 402 for transmitting the redirecteddata items. Interface 418 is a standard email application interface thatallows interaction between user 420 and MCD 116, wherein the receiveddata items may be presented, new data items may be created, or replymessages may be generated.

To facilitate routing, the IMS administrative domain relies on a set ofInitial Filter Criteria (IFC) when an S-CSCF node in the IMS layer 350Bis mapped to a corresponding SGW and associated ESS. The routing rulesto find and/or assign a suitable ESS may be embedded in the IFCprovisioned by either the network operator or the service provider. Theinformation may be deployed in an HSS database statically, wherein anassigned S-CSCF node is operable to download the IFC from the HSS when asubscriber's UE (e.g., MCD 116) registers.

It will be realized that the embodiment illustrated in FIG. 4 isexemplary of email service delivery in a session messaging mode whereina separate media channel (e.g., message flow path 416) is provided.Alternatively, email service delivery may also be effectuated in a pagemode (also referred to as immediate messaging mode) wherein theredirected data item information is carried within a signaling channel(e.g., signaling flow path 414).

FIG. 5 depicts a flowchart associated with one or more exemplaryembodiments of the present patent disclosure for effectuating deliveryof data items over IMS. At block 502, a new data item (e.g., emailmessage, calendar request, etc.) is available for a user, either at theuser's standalone desktop computer, user's networked computer in a LAN,or at a host/server system in an enterprise network. In a furthervariation, the data items may be available at an Internet mailboxassociated with the user, typically hosted by an Internet ServiceProvider (ISP), for example, as described in the co-pending commonlyassigned U.S. patent application Ser. No. 10/671,162 (filed: Sep. 25,2003), entitled “SYSTEM AND METHOD FOR PUSHING INFORMATION FROM A HOSTSYSTEM TO A MOBILE DATA COMMUNICATION DEVICE,” now published as U.S.Patent Application Publication No. 2004/0073619, in the names of: BarryJ. Gilhuly, Anh Ngoc Van, Steven M. Rahn, Gary P. Mousseau and MihalLazaridis, incorporated by reference herein. Regardless of where thedata items are available, the new data item may be automaticallydetected (block 504) or by means of a polling mechanism (block 506). Aredirector component processes and packages at least a portion of aninstance (i.e., the original data item or a copy thereof) into processedinformation, including adding address information relating to the user'sMCD (block 508). The processed information is then transmitted to anIMS-aware node, e.g., RSS service gateway (SGW) (block 510), whereby theprocessed information is delivered over the IMS network to a properservice client executing on the user's MCD that is accessible via anaccess network (block 512).

FIG. 6 depicts a flowchart associated with one or more exemplaryembodiments of the present patent disclosure for effectuating deliveryof a data item from an IMS-aware mobile communications device such as,e.g., MCD 116 shown in FIG. 1. An authorized user generates a data item(e.g., a new email message or a reply to a received message, a calendarrequest, or an IM message, etc.) using appropriate application softwareexecuting on MCD 116, whereupon the SC component executing thereonprocesses and packages the data item for delivery via IMS (block 602). Asuitable RAN couples MCD 116 to a service node in the IMS infrastructure(block 604), wherein the service node or its component (e.g., S-CSCF)queries an HSS node associated with the user's home network to determinerouting (block 606). Address information relating to the SGW that isassociated with the user's MCD and ESS is determined, whereupon the dataitem is transported to the SGW using either page mode or sessionmessaging mode (block 608). The SGW thereafter delivers the data item tothe ESS associated with the user for further transmission based uponintended recipient's address (block 610).

The IMS delivery model described in FIG. 4 for redirecting data items isrelatively simple and straightforward to implement in a number ofdifferent network environments. It will be realized, however, that sincean assigned S-CSCF node is operable to determine routing informationthat is static (as embedded within the IFC that populate an HSSdatabase), the IMS administrative domain is not capable of dynamicallyand intelligently monitor and adjust a transmission path between the ESSand a UE device based on the current runtime circumstances of the ESS inorder to maintain a reliable service path. In other words, reliance onthe use of the static bindings provisioned via the IFC to reach adestined ESS directly may cause reliability and scalability issues incertain network implementations.

FIG. 7 depicts a flowchart relating to a service gateway decompositionscheme 700 according to one embodiment wherein scalability andreliability concerns may be advantageously addressed. The decompositionscheme 700 involves decomposing media handling capability from signalingfunctionality of a full SGW node such as SGW 402 illustrated in FIG. 4,whereby a number of “thin” SGW nodes are controlled by a controllerentity of an IMS network (block 702). One or more gateway controllersthat are logically seen as a single controller node may be provided forembodying the signaling flow functionality (block 704). A number of SGWnodes may be provisioned in a scalable arrangement, each having mediahandling capabilities (block 706). The gateway controller is interfacedwith the gateways to effectuate a dynamically configurableinterconnection arrangement between the SGWs and ESS nodes (block 708).Essentially, the functionality of the gateway controller includesmonitoring and communicating with the SGWs, wherein the ESS nodes andSCs connect to and consult the gateway controller to obtain and usesuitable and reliable SGW nodes for service delivery. As illustrated,the communications between the SGW nodes and the gateway controller maybe effectuated using SIP messaging (block 710), or alternatively,H.248-based messaging (block 712).

FIG. 8 depicts a network architectural embodiment 800 for facilitatingdelivery of data items over IMS wherein service gateway functionality isdecomposed in accordance with the teachings set forth herein. Asexemplified, external network 405 in this FIGURE is the same as thenon-trusted domain depicted in FIG. 4 with respect to the non-decomposedSGW embodiment. One or more service gateway controllers (SGCs) 802 areinterfaced with ESS 404 with respect to effectuating a signaling flowinterface 810. Interface 812 is operable to effectuate media/messagetransport flow in a first protocol, which may be standards-based orproprietary as discussed previously, between ESS 404 and one or moreSGWs 804. As before, appropriate protocol conversion/translation 403 isprovided as part of the SGW functionality for handling the media/messagetransport in a second protocol via a network pathway 808 to SC 415executing on one or more MCDs 116. Because of the service gatewaydecomposition, two separate signaling flow paths are necessary: asignaling flow path 806 between SGCs 802 and SC 415 on MCDs 116 andanother signaling flow path 807 between SGCs 802 and SGWs 804. Whereasthe signaling flow path 806 is effectuated using IMS's SIP-basedsignaling, an implementer has a choice with respect to the signalingprotocol used for the flow path 807. In one implementation, H.248/Megacoprotocol may be used as the signaling communication protocol relative tothe flow path 807. Alternatively, Media Gateway Control Protocol or MGCPmay be used in another implementation as the signaling communicationprotocol between SGCs 802 and SGWs 804. In a still further variation,illustrated in FIG. 8, IMS's SIP signaling may be extended so that thecommunication between SGCs 802 and SGWs 804 may also be SIP-based. Inthis embodiment, accordingly, both SGC functionalities 802 as well asSGW functionalities 804 are deployed as IMS entities (i.e., AS nodes)wherein the service network arrangement coupling these componentsbecomes an extension of the IMS infrastructure. Accordingly, such anarrangement may afford the advantage of IMS's management capabilitiessuch as, e.g., security, charging, reliability, etc. extended even tothe service network environment. Further, it should be appreciated thatif the service network disposed between SGCs 802 and SGWs 804 becomesintegrated within the IMS infrastructure, the SGC and SGW nodes caninherit all IMS entity characteristics and be seamlessly managed by theIMS administrative domain. In addition, it is relatively morestraightforward to interconnect with other IMS networks when servicerequirements such as, e.g., roaming come into play.

On the other hand, implementing H.248 as the signaling protocol for theservice network between SGCs 802 and SGWs 804 does not allow the servicenetwork to become part of the IMS infrastructure inasmuch as the SGWnodes 804 are logically IMS-independent entities and as such existoutside the IMS administrative domain. However, in a further variation,the H.248/Megaco signaling communication may be adapted to run over SIP,wherein an H.248 context will be treated as a SIP extension that allowsintegration between H.248 and SIP.

FIG. 9 depicts a network communications environment 900 that illustratesa service network system 902 involving SGC 802 and SGWs 804.Additionally, the network communications environment 900 is illustrativeof a dynamically configurable routing arrangement 904 between SGWs 804and ESS nodes 404 at one end of the environment 900 as well as adynamically configurable routing arrangement 906 between SCs 415 andSGWs 804 with respect to IMS's message plane 908. It will be realizedthat although there may exist multiple SGCs based on a priority policyconfigured in an IMS node (i.e., HSS) with respect to a particularservice delivery (e.g., delivery of redirected email), logically theyare operable as a single centralized SGC, e.g., SGC 802, having a fixedand well known SIP URI, host/service (or resource) name, or a FullyQualified Domain Name (FQDN), and/or an IP address, which could beaccessed by the external entities such as ESS nodes 404 and SCs 415operating on respective MCDs 116. In general operation, SC 415 or ESS404 contacts SGC 802 using the IMS signaling plane to discover asuitable SGW. Responsive thereto, SGC 802 is operable to assign aparticular SGW to SC 415 or ESS 404. SC 415 establishes a messagingsession with the assigned SGW 804 that is already connected to aparticular ESS 404 with which SC 415 is associated. Alternatively, SGC802 may interrogate a target ESS (i.e., the ESS with which SC 415 isconfigured to communicate) to connect to the assigned SGW 804. Once theend-to-end path is established between SC 415 and the target ESS 404, SC415 may then receive the redirected data items as processed informationfrom ESS 404 via the particular SGW 404 assigned to the currentmessaging session. In order to maintain reliability and scalability, SGC802 may dynamically alter the assignment of SGWs 804 with respect to thevarious sessions between SCs 415 and ESS nodes 404 that may be going onat any one time. In other words, routing connection arrangement 904between SGWs 804 and ESS nodes 404 may be reassigned by SGC 802 suchthat an end-to-end message flow path between a particular SC 415 and theassociated target ESS 404 may be mediated by different SGWs at differenttimes. Likewise, routing connection arrangement 906 that illustratesrouting on the message plane 908 of the network environment 900 betweenSCs 415 and SGWs 804 may also be dynamically managed to further improvethe overall reliability and scalability of the service architecture.Additionally, since the signaling and messaging planes are separated dueto the service gateway decomposition, the service model illustrated inFIGS. 8 and 9 also provides protection against possible interferencebetween the two planes, which in turn helps to improve scalability.

FIG. 10 depicts a block diagram of an embodiment of a user equipment(UE) device 1000 operable as, e.g., MCD 116, for purposes of the presentpatent disclosure. It will be recognized by those skilled in the artupon reference hereto that although an embodiment of MCD 116 maycomprise an arrangement similar to one shown in FIG. 10, there can be anumber of variations and modifications, in hardware, software orfirmware, with respect to the various modules depicted. Further, UEdevice 1000 for purposes of the present disclosure may comprise a mobileequipment (ME) device without a removable storage module and/or a mobiledevice coupled with such a storage module. Accordingly, the arrangementof FIG. 10 should be taken as illustrative rather than limiting withrespect to the embodiments of the present patent application. Amicroprocessor 1002 providing for the overall control of UE 1000 isoperably coupled to a communication subsystem 1004 that may preferablybe capable of multi-mode communications (e.g., CS domain and PS domain).The communication subsystem 1004 generally includes one or morereceivers 1008 and one or more transmitters 1014 as well as associatedcomponents such as one or more local oscillator (LO) modules 1010 and aprocessing module such as a digital signal processor (DSP) 1012. As willbe apparent to those skilled in the field of communications, theparticular design of the communication module 1004 may be dependent uponthe communications networks with which the mobile device is intended tooperate (e.g., a CDMA network, a GSM network, WLAN, et cetera).Regardless of the particular design, however, signals received byantenna 1006 through appropriate access infrastructure 1005 (e.g.,cellular base station towers, WLAN hot spots, etc.) are provided toreceiver 1008, which may perform such common receiver functions assignal amplification, frequency down conversion, filtering, channelselection, analog-to-digital (A/D) conversion, and the like. Similarly,signals to be transmitted are processed, including modulation andencoding, for example, by DSP 1012, and provided to transmitter 1014 fordigital-to-analog (D/A) conversion, frequency up conversion, filtering,amplification and transmission over the air-radio interface via antenna1016.

Microprocessor 1002 may also interface with further device subsystemssuch as auxiliary input/output (I/O) 1018, serial port 1020, display1022, keyboard/keypad 1024, speaker 1026, microphone 1028, random accessmemory (RAM) 1030, a short-range communications subsystem 1032, and anyother device subsystems, e.g., timer mechanisms, generally labeled asreference numeral 1033. To control access, an interface 1034 operablewith a Universal Subscriber Identity Module or Removable User IdentityModule (USIM/RUIM) may also be provided in communication with themicroprocessor 1002. In one implementation, USIM/RUIM interface 1034 isoperable with a USIM/RUIM card having a number of key configurations1044 and other information 1046 such as identification andsubscriber-related data.

Operating system software and applicable service logic software may beembodied in a persistent storage module (i.e., non-volatile storage)such as Flash memory 1035. In one implementation, Flash memory 1035 maybe segregated into different areas, e.g., storage area for computerprograms 1036 (e.g., service processing logic), as well as data storageregions such as device state 1037, address book 1039, other personalinformation manager (PIM) data 1041, and other data storage areasgenerally labeled as reference numeral 1043. A transport stack 1045 maybe provided to effectuate one or more appropriate radio-packet transportprotocols. In addition, service client logic 1048 operable to effectuatesignaling and message pathways with respect to delivery and processingof redirected data items is also provided. It should be appreciated thatthe various operations set forth herein, either on the UE device side,ESS side, or on the IMS SGC/SGW side, may be accomplished via a numberof means, including software (e.g., program code), firmware, hardware,or in any combination, usually in association with a processing system.Where the processes are embodied in software, such software may compriseprogram instructions that form a computer program product, instructionson a computer readable medium, uploadable service application software,or software downloadable from a remote station, and the like.

Accordingly, in one exemplary embodiment, the structure andfunctionality of UE device 1000 may comprise one or more of thefollowing: means for contacting an SGC disposed in an IMS network by SC1048 executing thereon, wherein the SGC is operably coupled to aplurality of service gateways (SGWs); means for discovering a particularSGW assigned with respect to SC 1048 on wireless UE device 1000; andmeans for receiving from the particular SGW one or more data itemsredirected to the wireless UE device by a remote services serverassociated therewith.

It is believed that the operation and construction of the embodiments ofthe present patent application will be apparent from the DetailedDescription set forth above. While the exemplary embodiments shown anddescribed may have been characterized as being preferred, it should bereadily understood that various changes and modifications could be madetherein without departing from the scope of the present disclosure asset forth in the following claims.

1. A service network system adapted to interoperate in an InternetProtocol (IP) Multimedia Subsystem (IMS) environment, comprising: aservice gateway controller (SGC) operable to effectuate a signalinginterface with respect to at least one remote services server; and aplurality of service gateways (SGWs) operably coupled to said SGC, saidplurality of SGWs for effectuating a message transport interface withrespect to said at least one remote services server, wherein each ofsaid plurality of SGWs is configurable to be connected to said remoteservices server in a dynamic routing arrangement.
 2. The service networksystem as recited in claim 1, wherein each of said plurality of SGWsincludes means for converting a data item received from said remoteservices server in a first protocol into message information in a secondprotocol.
 3. The service network system as recited in claim 2, whereinsaid data item comprises one of an email message, a calendar event, ameeting notification, an address entry, a journal entry, a personalreminder, and an Instant Message (IM).
 4. The service network system asrecited in claim 1, wherein said SGC comprises a network nodeaddressable using a Session Initiation Protocol (SIP) Uniform ResourceIdentifier (URI).
 5. The service network system as recited in claim 1,wherein said SGC comprises a network node addressable using a resourcename.
 6. The service network system as recited in claim 1, wherein saidSGC comprises a network node addressable using an Internet Protocol (IP)address.
 7. The service network system as recited in claim 1, whereinsaid SGC comprises a network node addressable using a host name.
 8. Theservice network system as recited in claim 1, wherein said SGC comprisesa network node addressable using a service name.
 9. The service networksystem as recited in claim 1, wherein said SGC comprises a logicallycentralized SGC representing a plurality of SGCs.
 10. A method ofcommunication, comprising: contacting a service gateway controller (SGC)disposed in an Internet Protocol (IP) Multimedia Subsystem (IMS) networkby a service client (SC) executing on a user equipment (UE) device,wherein said SGC is operably coupled to a plurality of service gateways(SGWs); discovering a particular SGW assigned to said SC on said UEdevice; and receiving from said particular SGW one or more data itemsredirected to said UE device by a remote services server associatedtherewith.
 11. The method as recited in claim 10, wherein said one ormore data items comprise at least one of an email message, a calendarevent, a meeting notification, an address entry, a journal entry, apersonal reminder, and an Instant Message (IM).
 12. The method asrecited in claim 10, wherein said SGC is addressed using a SessionInitiation Protocol (SIP) Uniform Resource Identifier (URI) associatedtherewith.
 13. The method as recited in claim 10, wherein said SGC isaddressed using a resource name associated therewith.
 14. The method asrecited in claim 10, wherein said SGC is addressed using an InternetProtocol (IP) address associated therewith.
 15. The method as recited inclaim 10, wherein said SGC is addressed using a service name associatedtherewith.
 16. The method as recited in claim 10, wherein said SGC isaddressed using a host name associated therewith.
 17. The method asrecited in claim 10, wherein said contacting is effectuated over a radioaccess technology selected from IEEE 801.11a technology, IEEE 802.1btechnology, IEEE 801.11g technology, IEEE 802.1n technology, GSM/EDGERadio Access Network (GERAN) technology, Code Division Multiple Access(CDMA) technology, Universal Mobile Telecommunications System (UMTS)technology, and Evolution-Data Optimized (EVDO) technology.
 18. Awireless user equipment (UE) device, comprising: means for contacting aservice gateway controller (SGC) disposed in an Internet Protocol (IP)Multimedia Subsystem (IMS) network by a service client (SC) executing onsaid wireless UE device, wherein said SGC is operably coupled to aplurality of service gateways (SGWs); means for discovering a particularSGW assigned to said SC on said wireless UE device; and means forreceiving from said particular SGW one or more data items redirected tosaid wireless UE device by a remote services server associatedtherewith.
 19. The wireless UE device as recited in claim 18, whereinsaid one or more data items comprise at least one of an email message, acalendar event, a meeting notification, an address entry, a journalentry, a personal reminder, and an Instant Message (IM).
 20. Thewireless UE device as recited in claim 18, wherein said means forcontacting is operable to contact said SGC using a Session InitiationProtocol (SIP) Uniform Resource Identifier (URI) associated therewith.21. The wireless UE device as recited in claim 18, wherein said meansfor contacting is operable to contact said SGC using a resource nameassociated therewith.
 22. The wireless UE device as recited in claim 18,wherein said means for contacting is operable to contact said SGC usinga resource name associated therewith.
 23. The wireless UE device asrecited in claim 18, wherein said means for contacting is operable tocontact said SGC using an Internet Protocol (IP) address associatedtherewith.
 24. The wireless UE device as recited in claim 18, whereinsaid means for contacting is operable to contact said SGC using aservice name associated therewith.
 25. The wireless UE device as recitedin claim 18, wherein said means for contacting is operable to contactsaid SGC using a host name associated therewith.
 26. The wireless UEdevice as recited in claim 18, wherein said means for contacting isoperable to contact said SGC using a radio access technology selectedfrom IEEE 801.11a technology, IEEE 802.1b technology, IEEE 801.11gtechnology, IEEE 802.1n technology, GSM/EDGE Radio Access Network(GERAN) technology, Code Division Multiple Access (CDMA) technology,Universal Mobile Telecommunications System (UMTS) technology, andEvolution-Data Optimized (EVDO) technology.